tests: drivers: udc: Add support for uni-directional data endpoints#94345
Conversation
|
|
@jfischer-no, @tmon-nordic Can you please visit? |
|
I will not update this PR and will close it once #94766 is merged. |
|
@jfischer-no We're still encountering this as 4.3.0 approaches, and given #94766 doesn't appear like it's going to make it into that release, are you open to a test-only fix similar to the ones found here, but addressing your review comments? I believe something like c05f518 is more in line with your expectations for how to handle this? |
zephyrbot
added
the
area: Tests
|
Thanks Pete, I updated the PR according to your commit. It is ready for reviews. |
|
This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time. |
|
Re-opening since we really still need this for testing on MAX32 to work as expected. @jfischer-no can you review please? |
|
Needs rebase to pick up new SDK to fix failing CI. |
This commit adds separate selection for IN and OUT endpoint addresses. This change allows the test to work with devices that have uni-directional endpoints. Signed-off-by: Furkan Akkiz <hasanfurkan.akkiz@analog.com> Signed-off-by: Pete Johanson <pete.johanson@analog.com>
|
7 participants
Devices with uni-directional data endpoints fail on "tests/drivers/udc" test. This change introduces separate IN and OUT endpoint address selection and assigns suitable endpoint addresses for each direction to ensure the test runs successfully on such devices.